Subsystem Class
Represents the KINGSTAR Subsystem.
Inheritance Hierarchy
System.Object
IntervalZero.KINGSTAR.Local.Class.Subsystem
Namespace: IntervalZero.KINGSTAR.Local.Class
Assembly: IntervalZero.KINGSTAR.Local.Class (in IntervalZero.KINGSTAR.Local.dll) Version: 4.4.0.0
Syntax
public class Subsystem : ISubsystem
Public Class Subsystem Implements ISubsystem
The Subsystem class exposes the following members.
Constructors
Name | Description | |
---|---|---|
![]() |
Subsystem | A creator for the Subsystem class. This class contains the necessary information about controlling the KINGSTAR library. |
![]() |
Subsystem | A creator for the Subsystem class. This class contains the necessary information about controlling the KINGSTAR library. |
Methods
Name | Description | |
---|---|---|
![]() |
Dispose | Disconnects the application from KINGSTAR and releases any unmanaged resources. It is essential to invoke the Dispose method when the instance is no longer needed. |
![]() |
Log | Records the specified data in the logging shared memory. |
Remarks
- This class should always be called first.
- Multiple instances means you have multiple
ksRuntime.rtss
running at the same time and controlling different network cards. If you have Multiple Master Package, you can create several Subsystem classes which link to separate instances. For example, you have three Subsystem classes. They can use the instance zero, one, and two for each of them. If you don't have Multiple Master Package, you can create several Subsystem classes which all use the same instance, which is the instance zero. Several applications can link to one KINGSTAR Runtime, but one application can't link to several Runtimes. - One KINGSTAR Runtime = One
ksRuntime.rtss
.
See also